mev-boost: 1.8 -> 1.9-rc3 #602
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Flake lock file updates:
• Updated input 'nixpkgs-unstable':
'github:nixos/nixpkgs/dad564433178067be1fbdfcce23b546254b6d641?narHash=sha256-vn285HxnnlHLWnv59Og7muqECNMS33mWLM14soFIv2g%3D' (2025-02-20)
→ 'github:nixos/nixpkgs/f3a2a0601e9669a6e38af25b46ce6c4563bcb6da?narHash=sha256-KCtAXWwQs03JmEhP4ss59QVzT%2BrHZkhQO85KjNy8Crc%3D' (2025-03-23)
bbjubjub2494
force-pushed
the
bump-mev-boost
branch
from
e3f1d7a to
0a05bf4
Compare
bbjubjub2494
force-pushed
the
bump-mev-boost
branch
from
0a05bf4 to
c684bc4
Compare
Collaborator
Author
|
Supersedes #594 (which has unsigned commits btw) |
Contributor
|
mev-boost is at 1.9 release now anyway |
Contributor
|
I made a new mev-boost 1.9 PR to save you the trouble |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note the discussion in #574 about whether it is appropriate to include a release candidate. Since I do not know mev-boost, I do not take a position on this. I am simply fulfilling my promise to Martin to split up the PR.